Conditional communication forwarding based on origination and destination attributes

ABSTRACT

One example method of operation may include one or more of identifying an incoming call via a communication processing device, terminating the incoming call at a call management device, identifying one or more caller attributes received with the incoming call, comparing the one or more caller attributes to one or more call recipient preferences stored in a call recipient profile, and transmitting a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. non-provisional patent application Ser. No. 16/993,022 entitled, “CONDITIONAL COMMUNICATION FORWARDING BASED ON ORIGINATION AND DESTINATION ATTRIBUTES,” both of which were filed on the same day and each incorporated herein by reference in its entirety.

BACKGROUND

Conventionally, mobile device users receive calls from undesired sources every day and sometimes several times an hour depending on the particular day. The source numbers which are used to dial the users may be local numbers, long-distance numbers, anonymous numbers, spoofed numbers, etc. The calls may be spam calls, scam calls, robocalls, etc. With recent updates to smartphones and the call screen user interfaces used during a call, the sources of the calls are generally displayed in some capacity to permit the user to identify whether to answer the phone call or not, such as caller ID or other data services indicating a name and/or location origin of the number assigned to the caller. However, in the event that the number is not known to the caller or is matched to his or her previously stored contacts, the caller may require additional information to be shared to demonstrate credibility as a reputable service or advertisement and not just some arbitrary caller without a reputation or legitimate product/service to share with the caller.

There are generally limited tools available to demonstrate that the call is likely to be a scam or spam caller, or, a reputable caller, especially in real-time, so a caller can quickly decide whether to answer the call, drop the call, block the call, etc. With approximately 90 percent of business calls going unanswered, both ends users and callers require more advanced strategies for identifying callers and making informed decisions regarding whether to answer a call.

SUMMARY

Example embodiments of the present application provide at least a method that includes at least one of identifying an incoming communication via a communication processing device, identifying communication source attributes associated with a communication source of the incoming communication, retrieving one or more communication routing conditions from a communication recipient profile associated with an intended recipient device identified by the incoming communication, and determining whether to route the incoming communication to the intended recipient device or an automated communication management device based on the communication source attributes and the one or more communication routing conditions.

Another example embodiment may include an apparatus that includes a processor configured to identify an incoming communication via a communication processing device, identify communication source attributes associated with a communication source of the incoming communication, retrieve one or more communication routing conditions from a communication recipient profile associated with an intended recipient device identified by the incoming communication, and determine whether to route the incoming communication to the intended recipient device or an automated communication management device based on the communication source attributes and the one or more communication routing conditions.

Another example embodiment may include a non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform one or more of identifying an incoming communication via a communication processing device, identifying communication source attributes associated with a communication source of the incoming communication, retrieving one or more communication routing conditions from a communication recipient profile associated with an intended recipient device identified by the incoming communication, and determining whether to route the incoming communication to the intended recipient device or an automated communication management device based on the communication source attributes and the one or more communication routing conditions.

Still another example embodiment may include a method that includes one or more of identifying an incoming call via a communication processing device, terminating the incoming call at a call management device, identifying one or more caller attributes received with the incoming call, comparing the one or more caller attributes to one or more call recipient preferences stored in a call recipient profile, and transmitting a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences.

Yet another example embodiment may include an apparatus that includes a processor configured to identify an incoming call via a communication processing device, terminate the incoming call at a call management device, identify one or more caller attributes received with the incoming call, compare the one or more caller attributes to one or more call recipient preferences stored in a call recipient profile, and a transmitter configured to transmit a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences.

Still another example embodiment may include a non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform identifying an incoming call via a communication processing device, terminating the incoming call at a call management device, identifying one or more caller attributes received with the incoming call, comparing the one or more caller attributes to one or more call recipient preferences stored in a call recipient profile, and transmitting a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example communication management network configuration for conditional communication forwarding according to example embodiments.

FIG. 1B illustrates an example communication management network configuration for conditional communication forwarding with cloud call termination according to example embodiments.

FIG. 2 illustrates a user device graphical user interface of a customized call content configuration according to example embodiments.

FIG. 3 illustrates a logic diagram of a process for identifying caller data and forwarding customized communication information to a mobile device.

FIG. 4A illustrates an example system network flow diagram of a cloud based service for managing incoming communications according to example embodiments.

FIG. 4B illustrates an example system network flow diagram of a cloud based service for terminating calls in the cloud and managing subsequent communications according to example embodiments.

FIG. 5A illustrates an example flow diagram of a process for managing an incoming communication according to example embodiments.

FIG. 5B illustrates an example flow diagram of another process for managing an incoming communication according to example embodiments.

FIG. 6 illustrates an example network entity device configured to store instructions, software, and corresponding hardware for executing the same, according to example embodiments of the present application.

DETAILED DESCRIPTION

It will be readily understood that the components of the present application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of a method, apparatus, and system, as represented in the attached figures, is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments of the application.

The features, structures, or characteristics of the application described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments”, “some embodiments”, or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments”, or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In addition, while the term “message” has been used in the description of embodiments of the present application, the application may be applied to many types of network data, such as, packet, frame, datagram, etc. For purposes of this application, the term “message” also includes packet, frame, datagram, and any equivalents thereof. Furthermore, while certain types of messages and signaling are depicted in exemplary embodiments of the application, the application is not limited to a certain type of message, and the application is not limited to a certain type of signaling.

Example embodiments provide communication management for calls and other communications (e.g., messages, short message service (SMS) data, etc.). In one example, a new communication initiated by a particular caller/initiator may be intercepted and forwarded to a communication management device which is in the cloud and is configured to determine whether to allow a call, block a call, require certain CNAM data, require certain ECNAM data, apply user preferences of the intended recipient, etc. The communication management may result in a blocked call, a straight to voicemail call forwarding, a notification being sent to notify the recipient of the call, etc. Also, content management of content in associations with communications (CNAM/ECNAM data) to and from mobile device users may be customized and specific according to user profiles 122 which identify preferences for the types of enhanced data to receive, the types of calls to permit and not permit, etc.

One example embodiment may include a cloud service which manages a call termination and provides options contemporaneously with the cloud service maintain the call and notifying the end user device. In one example, a hardware store may be automatically calling a user device to have a delivery confirmed, the cloud server may answer and suspend the call pending further routing functions, an automated message may be played, such as “we are trying to locate your call recipient” along with playing music to keep the caller interested, or in the case of automation, to provide a feedback cue for maintaining the all, such as continuous audio. The call recipient may have their profile accessed and used to match the attributes of the caller to determine how to finalize the call connection process.

In another example embodiment, a call/communication may arrive at the call processing server, certain data present with the communication, certain data which is not present with the communication and any other data may be used by the call processing device in the cloud in an attempt to identify the calling party, such as CNAM data, registered scammer confirmation, enhanced CNAM data, etc. Then, the attributes identified from that call data analysis are used to generate a decision which matches the identified attributes to the user's preferences for how the call should be handled. For example, a user may order many deliveries from a particular hardware store and may be to select certain enhanced CNAM data that should be forwarded based on a call to the user's call device so as not to miss a delivery. However, the need to permit the call in its entirety may be unnecessary since modified information sharing may provide ample call related data for call management purposes.

FIG. 1A illustrates an example communication management network configuration 100 according to example embodiments. Referring to FIG. 1A, the content provider 110 is a server and/or database which stores and manages content, such as images, word strings/phrases, URL links and other data that is sent to one or more end user devices, such as mobile device(s) 102 as part of a CNAM/ECNAM data communication effort. The content provider 110 may assign the caller identification name (CNAM) data, such as data stored in a database 126, to certain callers which are registered to use the enhanced data services. Certain enterprise entities may desire to have enhanced data shared with their potential customers.

In operation, an enterprise entity 114 may have its own communication platform 112 to forward calls and/or messages to certain entities. For example, certain calling number(s) (‘A’ numbers) may be used to call/message any called numbers or ‘B’ numbers associated with the end user devices. The replacement CNAMs may be assigned through a portal application programming interface (API). The ‘A’ number party may be an enterprise entity network 114, which may include a call server or other calling entity, such as a third party responsible for managing communications and content pairing, CNAM data and other data shared with the called entities 102.

When a new communication is initiated 116, the communication processing platform 120 may include one or more servers 130 which are dedicated to processing the communication data to determine how to manage the communication based on the end user preferences. The server 130 may provide an interception function for calls sent from the enterprise which require a notification modification or added CNAM/ECNAM data. For example, an end user device 102 may want calls received to be sent to the device as a text message identifying a call and including certain portions of the CNAM/ECNAM data, omitting certain portions of the CNAM/ECNAM data and perhaps an option to drop/answer/re-route the call without any specific action taken by the end user. A carrier network may be integrated with the enterprise calls sent to and from the cloud server 130.

In one example, the call content associated with a call may be updated according to a call campaign effort to share advertising data and other content with the called devices 102. The results of the calls sent may be provided as feedback in an updated telemetry format, which includes calls answered, call times, content selected (i.e., URLs, video, etc.). A call campaign may include calling various ‘B’ numbers for various purposes such as updates to existing memberships, new offers and subscriptions, etc. The term ‘CNAM’ may include basic 15-character alphanumeric data or may be referring to an electronic CNAM (ECNAM), which may include images, video, audio, weblinks, characters in excess of 15 characters, etc. Use of the term CNAM in this specification may be associated with CNAM and/or ECNAM interpretations.

Once the communication has been intercepted and caller/source attributes 124 are paired with the communication, the modified communication 118 may include a transformation from an original communication (e.g., call with various ECNAM data), to a SMS message with only a portion of the ECNAM data, other data is blocked including the call. The message may have a capability to answer the call which may be ongoing and may include a timer, such as a thirty second countdown that is demonstrated in the SMS message along with a logo or a single word or phrase as compared to other data which is sent with the original communication.

FIG. 1B illustrates an example communication management network configuration for conditional communication forwarding with cloud call termination according to example embodiments. Referring to FIG. 1B, the configuration 150 may demonstrate another example where the cloud platform 120 terminates a call and suspends a call connection pending additional notification arrangements with the end user device 102. In this example, a call is initiated 152 which is then terminated 154 in the cloud at a call management server 140 which notifies an application server 130 that the call is received and is being maintained 142 pending additional processing decisions. Once the call is terminated, the call data 156 received with the call along with intended recipient profile information 122, caller attribute information 124, and decision made about the caller integrity can lead to a specific outcome, such as a modified communication 158 which includes some or all of the original call data or even a different format.

FIG. 2 illustrates a user device graphical user interface of a customized call content configuration according to example embodiments. Referring to FIG. 2 , the example provides a caller as a hardware store ‘ACME’ hardware 214, with a sub-notation 216 for the “delivery unit” and a company logo 218, all of which are forms of enhanced data. The first example device 210 has all those portions of enhanced data received with no preferences for blocking or limiting 232 such data. The user may then use the swipe arrow interface option 219 to accept or reject the call. In another example, the call data that is sent to the user device may include an incoming call notification 222 with only the logo 218 being permitted to be viewed for call acceptance 224 or rejection. The use device profile may indicate any type of call treatment option to limit the amount of information that is sent to the end user device and for certain requirements, such as only for callers which are registered as known trusted callers on a particular list. In another example a smart watch 230 that is linked to the smartphone may only show the logo 218 and the word delivery 216 which is a truncated version 234 of the original content. This enables a smart watch owner to quickly identify the caller and whether to permit the call or not.

FIG. 3 illustrates a logic diagram of a process for identifying caller data and forwarding customized communication information to a mobile device. Referring to FIG. 3 , the configuration 300 includes a call server 310 which represents the enterprise entity and the communication management process. When a call is placed to a customer, a portal 312 accesses a content API 314 to retrieve the enhanced content that is shared with the call. The call data may include the ‘A’ number of the calling entity, the ‘B’ number of the callee entity, the 15-character CNAM, the ENCAM data, extra text and any summary of information necessary to share the content with end user. The could application server 320 may include a rules engine 322 which decides whether the caller is reputable based on one or more attributes such as a known number, a registered number or name and other criteria. The call identification information engine 318 may pair the calling party information with the call communication based on the rules. When the decision is made to route the call, the call information may be routed with some, all or a specific arrangement as a message or call 332 to the end user device.

FIG. 4A illustrates an example system network flow diagram of a cloud based service for managing incoming communications according to example embodiments. Referring to FIG. 4A, the system configuration 400 may include a caller 410 which places a communication 422 such as a call or message 422 to the callee device 419. The caller data database 412 may be referenced to retrieve information about the caller, such as CNAM/ECNAM data, registered/trusted user data, etc. and such information is forwarded 424 to the call answering service 414 of the cloud services 420. The communication is received and processed to identify the information associated with the caller, such as what CNAM data or enhanced data is received, whether the caller is a known trusted entity or not, etc. The callee information may be retrieved and applied as well to determine how to forward the communication or not forward the communication.

The preferences associated with the callee profile can be used to drop the call, ensure the caller is reputable, only permit certain CNAM/ECNAM data, block the call or partially block the call by permitting a text message which identifies the call and certain enhanced data but does not permit the call, etc. The preferences are applied 426 and the call is forwarded to a service application which is used to route the communication/modified communication to the end user. For example, when the preferences indicate that only a logo or a part of the CNAM data should be forwarded via a text message while the call is dropped or sent to voicemail, then the modified communication 428 will be sent to the carrier network 418 via the service application 416. The caller data 432 that is included with the communication may include one or more of the caller data types depending on the user profile preferences and requirements. The modified data is forwarded 434 to the end user device 419.

FIG. 4B illustrates an example system network flow diagram of a cloud based service for terminating calls in the cloud and managing subsequent communications according to example embodiments. Referring to FIG. 4B, the configuration 450 includes a similar example to the example in FIG. 4A, however, this configuration provides for cloud call termination, and when a call is placed 452, the forwarded call and call data 454 is terminated in the cloud and the preferences and attributes are identified 456 to determine how to manage the call and how to notify the callee device 419. The pending call data is forwarded to the callee's carrier 458 so the caller data 462 and call can be forwarded 462 in a manner consistent with the callee preferences.

FIG. 5A illustrates an example flow diagram of a process for managing an incoming communication according to example embodiments. Referring to FIG. 5A, the process 500 may include identifying an incoming communication via a communication processing device 512, identifying communication source attributes associated with a communication source of the incoming communication 514, retrieving one or more communication routing conditions from a communication recipient profile associated with an intended recipient device identified by the incoming communication 516, and determining whether to route the incoming communication to the intended recipient device or an automated communication management device based on the communication source attributes and the one or more communication routing conditions 518.

The incoming communication is one or more of a call and a data message. The process may also include routing the incoming communication to the intended recipient device when the communication source attributes indicate a source type that is accepted by the one or more communication routing conditions. For example, a source that is known and trusted as identified from a list of trusted parties may be identified as an attribute that is acceptable for forwarding the call along to the end user device. A source that is not known may be required to have its enhanced data forwarded as a text message so the user device can avoid a potential scam call until the end user decides to permit the call or not. For example, a company logo in a text message may be a second leg of a terminated call and the user selecting to accept the call thereafter could be a third leg that actually connects the call. The process may also include routing the incoming communication to the automated communication management device when the communication source attributes indicate a source type that is not accepted by the one or more communication routing conditions, and performing one or more of forwarding the incoming communication to voice mail or blocking the incoming communication when the source type is not accepted by the one or more communication routing conditions. The process may also include determining the communication source attributes include one or more of a caller identification name (CNAM) and an enhanced caller identification name (ECNAM), and determining the communication source attributes satisfy the one or more communication routing conditions. The process may also include blocking a portion of the incoming communication when only a portion of the communication routing conditions are satisfied, and forwarding a notification to the intended recipient device comprising another portion of the incoming communication.

FIG. 5B illustrates an example flow diagram of another process for managing an incoming communication according to example embodiments. Referring to FIG. 5B, the process 550 may include identifying an incoming call via a communication processing device 552, terminating the incoming call at a call management device 554, identifying one or more caller attributes received with the incoming call 554, comparing the one or more caller attributes to one or more call recipient preferences stored in a call recipient profile 556, and transmitting a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences 558.

The process may also include determining the one or more caller attributes include one or more of a caller identification name (CNAM) and an enhanced caller identification name (ECNAM), and responsive to identifying the caller attributes include one or more of the CNAM and the ECNAM, transmitting the notification as a first type of notification identified from the one or more call recipient preferences. The notification may include one of a call, a message, and a voicemail. The message may include a portion of ECNAM data based on the ECNAM data identified. The process may also include maintaining the incoming call as an active call for a predetermined amount of time after the incoming call has been terminated, for example, the call may be maintained as active with a line hold for 30 seconds to see if the callee is willing to answer the call or not based on the notification provided to the user. The process may also include determining the caller attributes include a known caller identity identified from a trusted list of callers or an untrusted list of callers. The process may also include transmitting the notification, while the incoming call is active, as a first type when the known caller identity is trusted and a second type when the caller identity is untrusted. When the known caller identity is trusted, transmitting the notification with a confirmation identifying the caller as trusted, receiving a call answer confirmation from the call recipient device, and responsive to receiving the call answer confirmation, connecting the terminated call with the call recipient device.

The operations of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a computer program executed by a processor, or in a combination of the two. A computer program may be embodied on a computer readable medium, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.

FIG. 6 is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the application described herein. Regardless, the computing node 600 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In computing node 600 there is a computer system/server 602, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 602 include, but are not limited to, personal computer systems, server computer systems, thin clients, rich clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 602 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 602 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 6 , computer system/server 602 in cloud computing node 600 is shown in the form of a general-purpose computing device. The components of computer system/server 602 may include, but are not limited to, one or more processors or processing units 604, a system memory 606, and a bus that couples various system components including system memory 606 to processor 604.

The bus represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 602 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 602, and it includes both volatile and non-volatile media, removable and non-removable media. System memory 606, in one embodiment, implements the flow diagrams of the other figures. The system memory 606 can include computer system readable media in the form of volatile memory, such as random-access memory (RAM) 610 and/or cache memory 612. Computer system/server 602 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 614 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to the bus by one or more data media interfaces. As will be further depicted and described below, memory 606 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of various embodiments of the application.

Program/utility 616, having a set (at least one) of program modules 618, may be stored in memory 606 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 618 generally carry out the functions and/or methodologies of various embodiments of the application as described herein.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method, or computer program product. Accordingly, aspects of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present application may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Computer system/server 602 may also communicate with one or more external devices 620 such as a keyboard, a pointing device, a display 622, etc.; one or more devices that enable a user to interact with computer system/server 602; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 602 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces 624. Still yet, computer system/server 602 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 626. As depicted, network adapter 626 communicates with the other components of computer system/server 602 via a bus. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 602. Examples include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Although an exemplary embodiment of at least one of a system, method, and non-transitory computer readable medium has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the application is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions as set forth and defined by the following claims. For example, the capabilities of the system of the various figures can be performed by one or more of the modules or components described herein or in a distributed architecture and may include a transmitter, receiver or pair of both. For example, all or part of the functionality performed by the individual modules, may be performed by one or more of these modules. Further, the functionality described herein may be performed at various times and in relation to various events, internal or external to the modules or components. Also, the information sent between various modules can be sent between the modules via at least one of: a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device and/or via plurality of protocols. Also, the messages sent or received by any of the modules may be sent or received directly and/or via one or more of the other modules.

One skilled in the art will appreciate that a “system” could be embodied as a personal computer, a server, a console, a personal digital assistant (PDA), a cell phone, a tablet computing device, a smartphone or any other suitable computing device, or combination of devices. Presenting the above-described functions as being performed by a “system” is not intended to limit the scope of the present application in any way but is intended to provide one example of many embodiments. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with computing technology.

It should be noted that some of the system features described in this specification have been presented as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, or the like.

A module may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. Further, modules may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM), tape, or any other such medium used to store data.

Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

It will be readily understood that the components of the application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the detailed description of the embodiments is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that the above may be practiced with steps in a different order, and/or with hardware elements in configurations that are different than those which are disclosed. Therefore, although the application has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent.

While preferred embodiments of the present application have been described, it is to be understood that the embodiments described are illustrative only and the scope of the application is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto. 

What is claimed is:
 1. A method comprising identifying an incoming call via a communication processing device that is terminated at a call management device; comparing received one or more caller attributes to one or more call recipient preferences stored in a call recipient profile; and transmitting a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences; wherein the caller attributes being determined comprise a known caller identity identified from a trusted list of callers or an untrusted list of callers; wherein the notification is transmitted, while the incoming call is active, as a first type when the known caller identity is trusted and a second type when the caller identity is untrusted.
 2. The method of claim 1, comprising determining the one or more caller attributes comprise one or more of a caller identification name (CNAM) and an enhanced caller identification name (ECNAM); and responsive to identifying the caller attributes comprise one or more of the CNAM and the ECNAM, transmitting the notification as a first type of notification identified from the one or more call recipient preferences.
 3. The method of claim 2, wherein the notification comprises one of a call, a message, and a voicemail.
 4. The method of claim 3, wherein the message comprises a portion of ECNAM data based on the ECNAM.
 5. The method of claim 1, comprising determining the caller attributes comprise a known caller identity identified from a trusted list of callers or an untrusted list of callers.
 6. The method of claim 5, comprising when the known caller identity is trusted, transmitting the notification with a confirmation identifying the caller as trusted; receiving a call answer confirmation from the call recipient device; and responsive to receiving the call answer confirmation, connecting the terminated call with the call recipient device.
 7. An apparatus comprising a processor configured to identify an incoming call via a communication processing device that is terminated at a call management device; compare received one or more caller attributes to one or more call recipient preferences stored in a call recipient profile; and a transmitter configured to transmit a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences; wherein the caller attributes that is determined comprise a known caller identity identified from a trusted list of callers or an untrusted list of callers; wherein the notification is transmitted, while the incoming call is active, as a first type when the known caller identity is trusted and a second type when the caller identity is untrusted.
 8. The apparatus of claim 7, wherein the processor is further configured to determine the one or more caller attributes comprise one or more of a caller identification name (CNAM) and an enhanced caller identification name (ECNAM); and responsive to the caller attributes being identified as including one or more of the CNAM and the ECNAM, the transmitter is configured to transmit the notification as a first type of notification identified from the one or more call recipient preferences.
 9. The apparatus of claim 8, wherein the notification comprises one of a call, a message, and a voicemail.
 10. The apparatus of claim 9, wherein the message comprises a portion of ECNAM data based on the ECNAM.
 11. The apparatus of claim 7, wherein the processor is further configured to determine the caller attributes comprise a known caller identity identified from a trusted list of callers or an untrusted list of callers.
 12. The apparatus of claim 11, wherein when the known caller identity is trusted, the transmitter is configured to transmit the notification with a confirmation identifying the caller as trusted, and receive a call answer confirmation from the call recipient device, and responsive to the call answer confirmation being received, the processor is configured to connect the terminated call with the call recipient device.
 13. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform: identifying an incoming call via a communication processing device that is terminated at a call management device; comparing received one or more caller attributes to one or more call recipient preferences stored in a call recipient profile; and transmitting a notification, via the call management device, to a call recipient device based on the one or more caller attributes and the one or more call recipient preferences; wherein the caller attributes being determined comprise a known caller identity identified from a trusted list of callers or an untrusted list of callers; wherein the notification is transmitted, while the incoming call is active, as a first type when the known caller identity is trusted and a second type when the caller identity is untrusted.
 14. The non-transitory computer readable storage medium of claim 13, wherein the processor is further configured to perform: determining the one or more caller attributes comprise one or more of a caller identification name (CNAM) and an enhanced caller identification name (ECNAM); and responsive to identifying the caller attributes comprise one or more of the CNAM and the ECNAM, transmitting the notification as a first type of notification identified from the one or more call recipient preferences.
 15. The non-transitory computer readable storage medium of claim 14, wherein the notification comprises one of a call, a message, and a voicemail.
 16. The non-transitory computer readable storage medium of claim 15, wherein the message comprises a portion of ECNAM data based on the ECNAM.
 17. The non-transitory computer readable storage medium of claim 13, wherein the processor is further configured to perform: determining the caller attributes comprise a known caller identity identified from a trusted list of callers or an untrusted list of callers. 